Versions and Releases

Current and Upcoming Releases

The following table covers the main release dates - past, present and near future.

Prior to the 2023, the Pyramid release schedule was not been hardened. As of Q4-2024, this follows a more regimented timeline as described above and below

  • You can also see a more detailed enumeration of the version release history here.

Version

Release Date

End of Standard Support

End of Extended Support

2026 LTS - "Pythagoras"

Q4 2026

Q2 2027

Q1 2029

2025 "Newton"

Q1 2025

Q3 2026

Q2 2027

2024 LTS "Fibonacci"

Q4 2024

Q2 2025

Q1 2027

2023 "Archimedes"

Q2 2023

Q4 2024

Q2 2025

2020 LTS

Q3 2019

Q4 2023

Q1 2025

2018 LTS

Q4 2017

Q2 2020

Q4 2020
  • Green versions are currently supported
  • Orange versions are out of standard support
  • Red versions are out of extended support
  • White versions have not been released yet.

Release Framework

Pyramid Analytics offers a dual track release framework, providing a choice between ‘Long Term Support’ and ‘Feature Version Support’ releases.

  • Long Term Support (LTS) is a product life-cycle management policy in which a stable release of computer software is maintained for a longer period than the standard ‘feature’ edition. LTS describes a software edition that is supported for months or years longer than the software's standard edition, while also incorporating few or no changes to provide stability.
  • Feature Version Support (FVS) is a term that describes the software's standard or ‘feature’ edition. FVS software has a comparatively short life cycle and includes new, cutting-edge features. These features are generally omitted from the companion LTS edition until they have had time to mature - increasing the stability of the LTS release.

Version vs Release

“Version” and “Release” should not be confused.

  • Version refers to the type of release, i.e. Long Term Support or Feature Version Support.
  • Release refers to the numbered Pyramid release, for example ‘2025.00.132’. Generally speaking, it is possible to upgrade from a lower release number to a high release number.

It is always possible to upgrade from the LTS version to the FVS version and vice versa – as long as the upgrade is to a later release.

Release Tracks

LTS Versions

An LTS version is released every EVEN year and is supported for 2.5 years. It does NOT include new features.

  • Pyramid releases a primary LTS version in Q4 of the year (v2024 comes out in 2024 Q4).
  • It gets no new features, except certain data connectors. Its feature set is based on prior versions to the point of primary release.
  • Technical support on the version is for 2.5 years, with fixes available for that version:
    • Key bug fixes are included for the first 9 months.
    • Critical security updates are provided for another 24 months.
  • LTS versions are checked for upgradability:
    • Going back to the last LTS version (so 2024>2026, 2026>2028)
    • Going back to the last FVS main version, its last minor release and last two service packs (e.g. 2023.0>2024, 2023.10>2024, 2023.13>2024)

FVS Versions

An FVS version is released every ODD year and comes with both new features and all fixes (service packs “SP”).

  • Pyramid releases a primary FVS version in Q1 of the year (v2025 comes out in 2025 Q1).
  • New features are added for 15 months. (Minor items, like connectors may be added beyond that). After which, features go to the next release.
    • All bug fixes and security updates are provided for the first 21 months.
    • Key bug fixes are provided for a further 9 months.
    • Fixes are applied in an upcoming service pack.
  • FVS versions are checked for upgradability
    • Going back one main version, its last minor and last two service packs (e.g. 2023>2024, 2023.12>2024, 2023.13>2024)
    • Going back to the last two service packs of the prior main version (e.g. 2023.13 > 2025.0, 2023.14 > 2025.0)

The diagram below illustrates the release and version waterfall.

Track Considerations

LTS vs FVS

Customers that want a more robust, stable deployment will choose the LTS releases, which represent a more mature version of the platform, without the complications of brand-new features and new bug fixes that have the potential for regressions or follow-on issues. Unlike LTS versions, the ‘Feature’ FVS version with current bug fixes and features will have had less time to mature.

Customers wishing to stay in tune with the latest release, current bug fixes and new features can elect to deploy FVS versions. This protocol doesn’t preclude them from deploying the LTS versions, in sequence.

This overall approach is in line with the release cycles of many other applications and software frameworks in the market – and will give customers the ability to choose which track they wish to follow, with the freedom to switch at any time.

LTS Feature Gap

Customers choosing the LTS track will see new features roughly every 2 years. The features included will be capabilities released in prior versions and the last non-LTS version. While this represents a gap of time for new functionality, it does mean that the features included in the LTS release will have had a chance to mature before inclusion.

LTS Critical Security Patches

After roughly 9 months of key bug coverage for the LTS version, Pyramid will continue to release updates for the LTS version related only to CRITICAL SECURITY issues for another 21 months. These, in turn, will be limited to those that do not themselves require a significant change in the product or its architecture. A CRITICAL SECURITY issue normally relates to CRITICAL vulnerabilities found in 3rd party libraries or the product itself only. It does not include functionality of the application or changes in the 3rd party libraries. It also does not generally include adjustments for 3rd party libraries that become deprecated or lose support.

Switching Tracks

Customers can easily switch between versions of the product (LTS and FVS), as long as the upgrade is made with a later release of the product. In line with current Pyramid deployment protocols, an instance CANNOT be downgraded.

Upgrades

While all older versions of the platform can be upgraded to any newer release without implementing intermediate releases, Pyramid will only test certain combinations of upgrade (as described above). Regardless, Pyramid will support any upgrade combination with fixes if required.

Breaking changes are usually avoided at all cost, with exceptions for necessary changes caused by built-in to third party libraries and applications (like Python and R) which are unavoidable.

Support Schedule

Once a version is out of standard support, Pyramid will not issue any bug fixes for that version. Extended support will cover key bug fixes and critical security issues only. Customers should upgrade to the next release as soon as possible to avoid the scenario of having their deployment outside of support coverage.